Closing issue #183 #184
Closed
Closing issue #183 #184
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…via custom port number
|
Hello @skatrych This will not work and needs the client to support it and needs to be raised there. Merely altering the ports will not provide the desired functionality because the address advertised will be the original discovery port of 30303 and that is the port clients connect to. The proper alternative is to follow this up with [AWS] (kubernetes-sigs/aws-load-balancer-controller#1608). The intended functionality works perfectly in Azure, GCP, even locally on Minikube |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closing issue #183: enable p2p discovery port to have possibility of being exposed via custom port number